- Add logic to process holdout rules for feature flags
- Implement a method to determine variation for a holdout rule
- Create decision responses based on a holdout decision and its reasons
- Update logger messages for holdout rule evaluation

…ctConfigV4

- Change visibility of FEATURE_FLAG_BOOLEAN_FEATURE to public
- Change visibility of Variation VARIATION_HOLDOUT_VARIATION_OFF to public
- Update entityIds in HOLDOUT_BASIC_HOLDOUT and holdouts-project-config.json to use "$opt_dummy_variation_id" instead of hardcoded values

- Create test for checking if a user is in a variation for holdout feature when included in flags
- Implement test to verify exclusion of user from variation for holdout when specified as excluded from flags
- Add assertions to validate decision source, experiment, and variation for holdout feature

- Added public constant HOLDOUT_TYPEDAUDIENCE_HOLDOUT to class ValidProjectConfigV4
- Updated feature flag constants to public static in class ValidProjectConfigV4
- Updated holdout constants to public static in class ValidProjectConfigV4
- Created unit test userMeetsHoldoutAudienceConditions in DecisionServiceTest

…ecision class

…ith_holdout' to accurately reflect the functionality being tested

… metadata in OptimizelyUserContextTest

- Implement createOptimizelyWithHoldouts method to create Optimizely instance with holdouts
- Add test for decisionNotification with holdout scenario
- Update decide_for_keys_with_holdout test for holdout variations
- Implement decide_all_with_holdout test for multiple flag keys with holdouts

- Create Optimizely instance with specific configuration
- Set up decision notification handler for optimalizely decision notifications
- Test decision notification logic with holdout context
- Validate decision notification data for various test scenarios